How to get rudiments in is a subject often bothering not only to the beginning auditor. Frequently enough, the attempt to apply a rote procedure and “get rid of the ruds” has gotten into the way of establishing real communication with the pc and getting him into the shape to get audited, that is “willing to communicate with the auditor and interested in his own case”.
To give an orientation and establish some stable data as to how rudiments are handled (and how they should not be handled), the Qual Board has drafted this bulletin, taking up some of the misunderstoods that have haunted academy training here and there.
This issue does not cover alternative procedures the C/S can order for getting in the session rudiments, especially on pcs at the beginning of the bridge, like Lower Level Ruds (or plain 2WC as in “How are you?”), L1C, R2H or Big Mid Ruds. It focusses on flying “3 Ruds” or “6 Ruds” as the standard approach to get in out ruds.
3 Ruds or 6 Ruds are taught on Level 2. A HSDC/NED Auditor, Class 0 or Class 1 Auditor learns Lower Level Ruds, and these are what is usually applied on a beginning pc.
It is essential that the auditor first studies and understands the following reference materials on the subject of the procedure:
And also – with regards to the subject matter of rudiments themselves as case manifestation – the various references given on the Academy checksheets. It goes without saying that the basics of auditing as covered in the Basic Auditing Series must be very well understood and completely in on an auditor who attempts to bring out rudiments in on a pc.
It should be well noted that nowhere in the relevant reference bulletins it says that rudiments should be checked. However there is a common misunderstood that the rudiments are checked on the meter, much like the assessment on a prepared list. However to do so can cut the pc's comm line and disregards the technical fact that a meter can cease to react in the presence of out rudiments, especially of an ARC break (ref. HCOB 2 July 1962 Repetitive Rudiments).
Thus the auditor asks the rudiment question of the pc, and if the pc volunteers an answer that is an answer to the rudiment question, the auditor takes it up and handles it as given in the HCOB Rudiments, Definition and Patter.
The auditor then simple asks the rudiment question once more. The pc might have another answer which is taken up in the same way.
However, if the pc says no (or says so when the rud is asked for the first time), now the auditor can consult the meter. He checks the question and if no read and no F/N GIs he gets in the suppress button.
If there is a read, the auditor inquires further, if needed helping the pc with the meter, and, if he gets an answer, now – having a reading rudiment at hand – takes it earlier similar to F/N.
If the read does not disappear but the pc has no answers and/or protests or invalidates it, seems ARC broken by the read or seems resigned, or starts to explain how things have been run before, the auditor checks for false read.
“Has anyone said you had a … when you didn’t have one?” Get who, what, when and take it earlier, if necessary, to F/N.
If the auditor does not get a read when he checks the question after a “no” answer by the pc, even after using the suppress button, there is nothing that can be taken up and the auditor goes to the next rudiment question.
It is an invalidation if a pc answers a rudiment question by saying he has an out rud of this type and the auditor does not accept the answer because “the question has not read”. In HCOB 13 April 1964 Tone Arm Action it says,
“In a conflict between pc and meter, take the pc’s data. Why? Because Protest and Assert and Mistake will also read on a meter. You can get these off, but why create them? Your data comes from the pc and the meter always for anything. And if the pc’s data is invalidated you won’t get a meter’s data. If the pc says he has a PTP and the meter says he doesn’t, you take the pc’s data that he does.”
Very rarely it is necessary to go past life in handling a rud. When an auditor realizes that he bogs down in an E/S chain he should abandon it without taking it to F/N GIs and take up the original out rud the pc has given and try to handle it in PT without going E/S, using Lower Level Ruds procedure. If he cannot get this to an EP, he sends the folder to the C/S for new instructions.
The materials say that the button must be put in by the auditor. How does one get a button in on the pc? You simply let the pc say what has been suppressed (as given in HCOB 29 January 1970, Null Lists in Dianetics – of course you wouldn't say “that reads” today.) And there might be more than one answer. This is very much like the use of the button in Big Mid Ruds: You repeat the question for a suppressed until there is no further answer. Now the button is “in” and you can recheck or re-ask the rudiment question. If it still does not read and the pc has no answer that is now available, that's it.
If your last session was only a few days ago the C/S usually will be “Fly a Rud if no F/N”. If there was a break of some weeks, it is more probably “Fly 3 Ruds”, or in specific cases the C/S might order to fly “6 Ruds” or “all ruds”, including overts, invalidation and evaluation.
If it is just “Fly a Rud”, you go until the first F/N accompanied by VGIs and that's it. You can now bridge over to the major action you are expected to run in this session.
Of course in the case of Fly 3 Ruds it is different. First of all, each rud must be gotten to an F/N. But there is more to it: As mentioned above, the pc might very well have more than one ARC break which he experienced and which was not relieved by auditing since. The same goes for the other rudiments. This is especially true if a longer time has elapsed since your last session.
Because of this, it is advisable that you again ask for an ARC break (or whatever rud you are at) after you got an F/N. The pc might bring up another one, and another one. Only when the pc indicates that there are no more out ruds of this type and you have an F/N along with it (or get no read on checking the question even with the use of the suppress button), that's it, and you go on with the next rudiment question.
When your pc is not accustomed to this type of rudiment running, he might need a suitable R-factor so he does not feel invalidated or misunderstood when you ask the same rudiment question again and again.
The auditor has to be familiar with the references mentioned at the beginning of this bulletin and should drill the procedure until he has it down pat.